Simple Parity-Check Bit Computation for Polar Codes Cross-Reference to Related Applications

[0001] The present application claims priority to Provisional Application No. 62/570,463 filed October 10, 2017, entitled "Simple Parity-Check Bit Computation for Polar Codes," the contents of which are incorporated by referenced herein. Technical Field

[0002] The present disclosure relates to polar codes in wireless

communications and, in particular, parity-check bit computation for polar codes.

Background

[0003] Polar codes, proposed by Arikan [1 ], are the first class of constructive coding schemes that are provable to achieve the symmetric capacity of the binary-input discrete memoryless channels under a low-complexity Successive Cancellation (SC) decoder. However, the finite-length performance of polar codes under SC is not competitive compared to other modern channel coding schemes such as Low-Density Parity-Check (LDPC) codes and turbo codes. Later, SC List (SCL) decoder is proposed in [2], which can approach the performance of optimal Maximum-Likelihood (ML) decoder. By concatenating a simple Cyclic Redundancy Check (CRC) coding, it was shown that the

performance of concatenated polar code is competitive with that of well- optimized LDPC and turbo codes. As a result, polar codes are being considered as a candidate for future Fifth Generation (5G) wireless communication systems.

[0004] The main idea of polar coding is to transform a pair of identical binary- input channels into two distinct channels of different qualities, one better and one worse than the original binary-input channel. By repeating such a pair-wise polarizing operation on a set of 2 ^M independent uses of a binary-input channel, a set of 2 ^M "bit-channels" of varying qualities can be obtained. Some of these bit channels are nearly perfect (i.e., error free) while the rest of them are nearly useless (i.e., totally noisy). The point is to use the nearly perfect channel to transmit data to the receiver while setting the input to the useless channels to have fixed or frozen values (e.g., 0) known to the receiver. For this reason, those input bits to the nearly useless and the nearly perfect channel are commonly referred to as frozen bits and non-frozen (or information) bits, respectively. Only the non-frozen bits are used to carry data in a polar code. Loading the data into the proper information bit locations has direct impact on the performance of a polar code. An illustration of the structure of a length-8 polar code is illustrated in Figure 1.

[0005] In general, the set of information bit locations used to carry data varies with the number of channel uses, or equivalently the code length, N as well as the number of data bits, or equivalently the number of information bit locations, K. However, with the commonly used additive white Gaussian noise (AWGN) channel model, for any code length N, if K < K ₂ , then the information set A with K information bit locations is always a (proper) subset of the information set A ₂ with K ₂ information bit locations. As a result, with AWGN channel, for any given code length N, to specify the information sets for all possible number of information bit locations, K, one needs only to store a ranking sequence S _N of bit location indices of length N so that the last (or the first, depending on whether the bit-channel qualities are sorted in ascending or descending order) K indices in S _N is the set of information bit locations if there are K data bits, for any K e {1,2, ^••• , N}. Such a ranking sequence S _N is referred to as the information sequence or Polar sequence, from which the locations of bit-channels for carrying any number of data bits K can be derived. [0006] Figure 2 illustrates the labeling of the intermediate information bits s , where I e {0,1, "·,η} and i e {0,1, -- - . N - 1} during polar encoding with N = 8. The intermediate information bits are related by the following equation: si+ = si,i ® s _{l i+2} i, for i 6 {j 6 {0,1, - , N - 1}: mod Q^] , 2) = 0} and I e

{0,l, - , n - l}

s _{l+l i+2} i = s _{l i+2} i, for i E {j E {0Χ ·· · , Ν - = 0} and I e

{0,l, - , n - l}

with s _{0 j} ≡ ui be the info bits, and s _{n i} ≡ x _t be the code bits, for i e {0,1, -- - . N - 1}.

[0007] As mentioned above, the bit-channels indices of a Polar code of any given size N can be sorted (e.g. , in ascending order) into an index ranking sequence according to their relative qualities or reliabilities when carrying data.

Such a sequence that ranks the bit-channel indices is commonly called an information sequence or a Polar sequence.

[0008] In the 5G-NR standard, the information sequence or Polar sequence of a Polar code of any size N, up to a maximum of N _max , is chosen as a sub- sequence of another Polar sequence, denoted by Q^- ¹ = {^-,ρ"-,...,^-^}, of bit channel indices for the largest supportable size N _MAX , where N≤ N _MAX .

[0009] This Polar sequence Q^- ¹ = {ρ"- ,ρ"- ,.,.,ρ"™^} is given by Table 1 , where o≤g ^jV - <N _m3K -i denotes a bit index before Polar encoding for / = o,i,...,N-i and =1024. The Polar sequence Q^- ¹ is in ascending order of reliability

W{Q"™)<W{QI™)< ... <W{Q _N ^N -_ ₁ ), where W(Q?™*) denotes the reliability of bit index

[0010] For any code block encoded to N bits, where N≤ N _MAX a same Polar sequence Q^ ^_1 = feo ,Q" ,Q? ,-,QN-I} is used, which is a subset or sub- sequence of Polar sequence Q^ ¹ with all elements {(? ^max } of values less than N , ordered in ascending order of reliability ^W (Q« ) ^<W (QI ) ^<W (QI )<- ^<W (Q ^N -I) .

mo -) „ ^■ - n k> -■- ) (/■·- rr io " I a k> ^■■ ) « ((> ^■■ I II U> ^■ ) a ., il k) - ) ( ..·· ir(( ⁾ - 1 () -

128 518 256 94 384 214 512 364 640 414 —.i 819 :· 866

1 129 54 257 204 385 309 513 654 641 223 814 897 755

2 130 83 258 298 386 188 514 659 642 663 770 439 898 858

131 57 259 400 387 449 515 335 643 692 — 929 ¾? 840

4 132 521 260 608 388 217 516 480 644 835 772 490 900 830 5 1:33 1 12 261 352 389 408 5¾7 315 640 619 773 623 m 811 g 32 m 135 262 325 390 609 ms 221 646 472 671 902 871

1:35 78 263 533 m 596 s:i:9 370 455 739 903 638 m 289 264 155 382 551 520 613 796 776 916 804 1:33 194 255 210 393 650 521 422 809 463 805 478 m 85 266 305 384 229 522 425 550 714 843 806 846

11 ^■ 276 21 ^" 547 395 159 523 451 651 721 779 381 907 750

2 17 140 522 213 300 420 524 614 652 837 780 497 908 868

10 58 21ΐ 109 397 310 525 543 653 716 781 930 909 508

14 18 142 168 270 184 398 541 526 235 654 864 ^" 32 821 910 861

15 128 143 139 2 ^" 534 399 773 527 412 655 810 783 726 91 1 757

: 12 144 272 537 400 610 528 343 656 606 784 961 912 870

- 145 273 1 15 401 657 529 372 657 912 785 872 913 818 is 274 167 40.2 030 775 508 722 786 492 9 875 IS 20 280 27S 225 40.3 1 19 531 317 658 696 631 a¾:s 862 20 256 148 89 276 326 404 600 532 550 377 788 729 ms 758 21 34 290 Wt 306 405 339 5S3 426 661 435 700 8i¾ 848

22 24 529 278 772 406 218 453 662 817 750 443 8i¾ 877 23 m 524 27S 157 407 368 5S5 237 653 319 741 823

24 152 196 280 656 652 536 559 621 792 845 820 872

25 129 153 141 281 329 mm SiSS 230 537 833 : : ^■ : 812 920 821 761

21 154 101 282 1 10 m QiiiS 391 538 804 484 794 382 Ϊ22 877

27 512 155 147 2-; : 1 17 mm 313 539 712 430 795 822 ^■ :2 : 852

28 156 176 284 212 mm 450 540 834 668 838 851 824 485

29 40 157 142 285 171 mm 542 541 661 YS. 667 730 825 703

30 158 530 2-;: 776 mm 334 542 808 670 488 798 498 ^■ :23 835

: 130 159 321 287 330 s 233 543 779 671 239 799 880 827 878 32 19 1:60 31 288 226 555 544 617 672 378 800 742 928 883 S3 13 1:6:1 200 289 549 774 545 604 673 459 80:1 445 929 762

48 1:62 90 298 538 4:is 175 546 433 674 622 302 471 838 503

14 1:63 545 m 387 123 547 720 675 627 303 635 833 825 S6 72 292 292 308 420 658 548 816 676 437 304 932 832 878

37 257 ^■ : ^■ : 322 2·: : 216 421 612 549 836 : ^■ — 380 805 687 735

38 21 ^■ : :- 532 294 416 422 341 550 347 818 806 903 834 883

132 ^■ :- 263 2·: ·: 271 423 551 897 :·- ^■ : 461 807 825 885

40 35 ^■ 149 2·: : 279 424 220 552 243 680 496 808 500 838

41 258 102 297 158 425 314 553 662 669 809 846 837 884

42 170 105 298 337 426 424 554 454 682 679 810 745 838 880

43 513 304 299 550 427 395 555 318 724 ■: 826 838 826

44 80 172 296 300 672 428 673 556 675 684 841 812 732 840 764

45 37 m 163 30:1 1 18 429 583 557 618 685 629 446 m 841

25 174 92 302 332 430 355 558 898 686 351 314 962 867

47 m 47 SOS 579 43! 287 558 781 587 467 936 843 886

:SSS48:SSS 136 m 267 304 540 432 183 560 376 688 438 475 831

49 260 — 385 389 433 234 561 428 688 737 S 17 853 847

50 264 546 : :· 173 434 125 ^■ : :-2 665 680 251 818 867 846 507

51 38 179 324 307 121 435 557 563 736 1ΐ 462 819 637 847

52 514 180 208 308 553 436 660 564 567 1ΐ2 442 820 907 848 884

53 386 309 199 437 616 565 840 441 i2 487 848 751

54 182 150 310 784 438 342 625 684 469 822 695 850 842

41 183 153 311 179 439 316 567 238 685 247 823 746 851 886

^■ : : 144 184 165 312 228 440 241 568 359 683 824 828 852 871

57 28 185 106 313 338 441 778 569 457 687 842 825 753 853 880 SS m 3J4 312 563 570 399 6S8 738 820 854 804 508

58 42 im 328 3JS 704 443 345 571 787 698 899 823 857 805 848

516 536 31:6 390 452 572 591 670 323 504 856 873 SS 49 m 577 174 397 573 678 701 783 325 799 857 1000

62 74 m 548 m 554 403 434 702 849 330 255 858 882 63 272 ^■■ : 1 13 31:8 581 207 677 703 820 964 858 850

160 ^■ : 2 154 320 393 448 674 576 349 704 728 i 2 909 860 863

520 ^■■ : : 79 :2- 283 449 558 577 245 705 928 833 719 ^■ 758

:·: 288 194 269 :22 122 450 785 578 458 791 834 477 ^■ : :2 1008

"r 528 195 108 ?23 448 451 432 579 666 707 367 835 915 863 510

192 578 324 353 452 357 580 620 708 901 -- V: 638 864 878 ■: 544 T 224 325 561 453 187 581 363 709 630 ; r 748 865 853

70 70 : t 326 203 454 236 582 127 710 685 838 944 5" 763 71 m 519 327 63 455 664 083 191 m 844 S38 869 867 874 72 131 20C 552 32S 340 456 624 084 782 m> 633 340 491 90S 854 73 81 2 195 32S 394 457 587 085 407 ms 71 1 3 1 699 90S 878

50 202 270 338 527 458 780 586 436 7 14 253 S 2 754 87C 881

73 203 641 33:1 582 458 705 087 626 691 858 87:1 882

15 204 523 332 556 468 126 588 571 824 478 872 827

— 320 205 275 181 461 242 589 465 902 845 968 <r : 885

78 133 . ^: . 580 334 295 462 565 590 681 718 686 846 383 874 765 - ^■ : 52 207 291 335 285 463 398 591 246 719 740 847 910 ^■ re- 956

80 23 208 59 : ^■ 232 464 346 592 707 720 850 848 815 887

134 209 169 337 124 465 456 593 350 375 849 976 '.— 985

384 210 560 338 205 466 358 594 599 444 850 870 978 997

76 1 14 339 182 467 405 595 668 470 851 917 ^■ :-ς- 986

84 137 212 277 340 643 468 303 790 724 483 852 727 980 943

85 82 213 156 341 562 469 569 597 460 725 415 853 493 981 891 S6 56 87 3 2 286 470 244 598 249 726 485 873 982 998 W 27 s 197 343 585 m 595 599 682 727 905 855 701 983 766 S8 97 21® 1 16 299 432 189 880 573 728 795 931 984 511 m 39 170 354 433 566 881 41 1 473 756 98S 988

90 259 i 61 ¾ 211 474 676 602 803 730 634 858 860 :a 1001

91 84 219 531 347 401 475 361 603 789 731 744 859 499 987 951

138 220 525 348 185 476 706 604 709 732 852 860 731 988 1002

93 145 642 349 396 477 589 605 365 733 960 823 989 893

94 261 281 350 344 478 215 440 734 865 922 990 975

95 29 223 278 351 586 479 786 607 628 735 693 874 991 894 ς·: 43 224 526 352 645 480 647 608 689 -?: ^■ 797 864 918 992 1009

<r 98 225 177 353 593 481 348 609 374 -?- 906 865 502 993 955

98 515 226 293 354 535 482 419 610 423 738 715 866 933 994 1004 99 88 22? 388 ass 240 483 406 m 466 739 807 867 743 995 1010 m 140 228 91 356 206 484 464 793 474 S68 760 996 957

101 30 223 584 -- 95 48S 680 S:i3 250 636 sea 881 997 983

146 238 769 358 327 486 801 mi 371 694 494 9Sg 958 m 71 231 198 359 564 487 362 615 481 743 254 702 999 987

262 172 360 800 488 590 :· : 574 744 717 872 921 1000 1012

05;;;;; 265 233 120 402 489 409 :· - 413 745 575 i-: 501 1001 999 mm- 161 234 201 .L 356 490 570 :· 603 746 913 874 876 1002 1016 mm 576 235 336 307 491 788 :· ^■ : 366 747 798 875 847 1003 767 mm 45 62 364 301 492 597 620 468 748 81 1 ί-:- 992 1004 989 mm 100 2;- 282 365 417 493 572 655 749 379 877 447 1005 1003 mem 640 238 143 366 213 494 219 900 750 697 878 733 1006 990

51 239 103 367 568 495 31 1 623 805 751 431 879 827 007 1005 m 148 178 368 832 496 708 824 615 7S2 607 880 934 *QQ8 959

: 46 294 369 588 497 598 625 684 753 489 881 882 *QQ9 1011

114 75 93 378 186 m 601 62S 710 866 882 937 mm 1013 ias 266 J 644 371 646 m 651 627 429 723 883 963 m 895

273 202 372 404 421 628 794 756 486 747 mm 1006

517 245 592 373 227 501 792 252 757 908 885 505 1013 1014

^■ i 104 246 323 374 896 502 802 ^■ : κ 373 758 718 ii ^■ 855 1014 1017

· ^■ : 162 247 392 375 594 503 61 1 ^■ : r 605 759 813 887 924 1015 1018

120 53 248 297 r: 418 504 602 848 760 476 888 734 : 991

193 249 770 ?— 302 505 410 690 T 856 889 829 1017 1020

22 152 250 107 r; 649 506 231 634 713 ^" Γ2 839 890 965 1018 1007

123 77 251 180 379 771 507 688 635 632 -:? 725 891 938 1019 1015

124 164 252 151 380 360 508 653 482 764 698 884 1020 1019 1:25 768 253 209 381 539 sm 248 637 806 s 914 S93 506 *02J 1021 i¾6 268 284 382 1 11 369 638 427 3586 752 894 749 $022 1022 m 274 255 648 SSS 331 m 190 SS9 904 868 945 ¾023 1023

Table 1 : Polar sequence ¹ and its corresponding reliability wig? )

[0011] Polar codes may be used with parity check (PC) bits. Because the minimum-distance property of Polar codes is typically not good, an outer code is often used in combination of a polar code to improve its performance. The encoder of such a concatenation of Polar code and an outer code is shown in Figure 3, where the outer code is sometimes referred to as a Parity Check (PC) code. Such an outer code, or PC code, generates PC bits based on the data bits, in such a way that each PC bit depends only on the data bits placed before it (but not after it) according to the decoding order in a successive (list) decoder. This property allows an SCL decoder to take advantage of the known relationship between data bits and PC bits to trim the candidate paths during list decoding and thus get rid of the erroneously decoded paths from the list of candidate paths, which in turn improves the error performance of the decoder. The PC bits are sometimes referred to as PC frozen bits or dynamic frozen bits in the 5G-NR standard.

[0012] Denote Qf as a subset of bit indices in Polar sequence Q^ ¹ , and Qf as the subset of other bit indices in Polar sequence Q^- ¹ , where Q denote the indices of bit-channels used to carry either data bits or parity check bits, and Qf denotes the indices of bits channels that are frozen to known values. Thus, we have |Q | = κ + n _pc , |Qf | = N - |Q | , where K denotes the number of data bits, and n _pc is the number of parity check bits.

[0013] In the 5G-NR standard, the location of the PC bits (i.e., the bit indices associated with these PC bits) are computed as follows: Let = {G ₂ f ⁿ denote l o

the tt -th Kronecker power of matrix G ₂ , where G ₂ For a bit index j with

l l j = o,i,..., N - 1 , denote g _; . as the j -th row of and w(g _; .) as the row weight of g _; , where w(g _; .) is the number of ones in g _; . Denote the set of bit indices for PC bits as Q~ _c , where |Q The PC bits are divided into two kinds: A number of (i ) parity check bits are placed in the {n _pc - «™) ^least reliable bit indices in Q . A number of «™ other parity check bits are placed in the bit indices of minimum row weight in Q , where Q denotes the Q/| - n _pc ) most reliable bit indices in Q ; if there are more than «™ bit indices of the same minimum row weight in Q , the «™ other parity check bits are placed in the «™ bit indices of the highest reliability and the minimum row weight in Q . [0014] Generate u = [u ₀ u ₁ u ₂ ... u _{N 1} ] according to the following: k = o ;

if n _pc > 0

y ₀ = ⁰ ; y _x = o ; y ₂ = o ; y ₃ = o ; y, = o ;

for n = 0 tO N - l

if »€Q

if w e Q^ _C

"„= >¾ ;

else

M„ = c _k ;

^ = ^ + i ; end if

else

u„ = o ;

end if

end for

[0015] In the 5G-NR standard, one possible number of PC bits is 3, i.e. n _PC = 3. Given the locations of the n _PC PC bits, the 5G-NR standard may compute the values of the PC bits using a length-5 shift register. Specifically, the PC frozen bits value may be generated by a p-length (e.g. , p=5) cyclic shift register operation like below:

1 . initialize a p-length cyclic shift register, y[0], ... ,y[p-1 ], to 0

2. go through the elements in [uo, ui, U2, ... , UN-I],

- cyclic left shift the register: y[i] = y[(i-1 ) mod p] for i = 0,1, -· , ρ - 1.

- if the /-th sub-channel is information: set y [0] = (u, XOR y[0])

- if the /-th sub-channel is PC frozen: set u, =y [0]

Summary

Problems with Existing Solutions

[0016] There currently exist certain challenge(s). For example, where 3 PC bits may typically be used in the concatenation of Polar code and PC outer code, a shift-register computation of length 5 is used. However, as constructed, the first PC bit does not depend on any info bits and thus reduces to a regular frozen bit in most cases. Even the 2nd PC bit is also frozen in a significant number of cases. Only the last PC bit is not frozen in most cases. As a result, the effective number of PC bits is often much less than 3, and as a result, the performance benefit of such a small number of PC bits, if any, is quite limited.

[0017] On the other hand, because the last PC bit is often situated far away from the first info bit, the shift register computation is non-trivial and incurs significant additional delay and computational complexity, which is hard to justify when the performance benefit is negligible.

Brief Summary of Some Embodiments of the Present Disclosure/Solution [0018] Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Parity Check (PC) bits generated by certain outer code, are often placed at certain known specific locations to enhance the performance of SC or SCL decoding of Polar codes. These PC bits are often data dependent so that the decoder can take advantage of the known relationship of these PC bits with other data bits to enhance the Polar code performance. Particular embodiments include simple and effective methods of computing the PC bits. According a particular embodiment, each PC bit is computed by simply performing modulo-2 addition of all the data bits placed in front of the PC bit. This can be implemented using a size-1 shift register, which is simple. According to another embodiment, all PC bits are functions of K_PC least reliable PC bits, where K_PC may be a fixed constant or may be

determined based on the code rate of the Polar code. In a special case of this embodiment, the PC bits are simply repetition of the K_PC least reliable PC bits.

[0019] Particular embodiments use a simple, low complexity method of coupling some data bits with a special set of "artificially" known bits called Parity Check (PC) bits. The values of these PC bits are data dependent. Two groups of embodiments are described herein, one summing over all previous data bit values, and the other summing over a subset of the least reliable data bits according to a pre-determined parity check matrix.

[0020] There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. According to some embodiments, a method performed by a wireless transmitter for encoding information bits comprises: receiving a set of information bits; determining a set of parity check bits; concatenating the set of information bits with the set of parity check bits; Polar encoding the information bits into a set of information bits and frozen bits; and transmitting the encoded set of information bits to a wireless receiver. In particular embodiments, each parity check bit in the set of parity check bits is the binary sum of the values of all bits in front of it (either including or excluding other parity bits in front). Other embodiments include generating a set of parity check bits based on a systematic block code on the least reliable bits of the set of information bits.

[0021] According to some embodiments, a method performed by a wireless receiver for decoding information bits comprises: receiving a set of polar coded information bits concatenated with a set of parity check bits, wherein each parity check bit in the set of parity check bits is determined as described in the embodiments above; decoding the set of polar coded information bits

concatenated with the set of parity check bits; and terminating the decoding when one of the parity check bits in the set of parity check bits indicates an error.

[0022] Certain embodiments may provide one or more of the following technical advantage(s). Particular embodiments improve the error performance of the Polar code (e.g., by reducing the block error rate) with little increase in computational complexity. Another advantage is to provide early termination benefits, because any of the PC bits may be used for error detection. [0023] Various other features and advantages will become apparent to those of ordinary skill in the art, in light of the following written description and accompanying drawings. Brief Description of the Drawings

[0024] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0025] Figure 1 is an illustration of the structure of a length 8 polar code, according to exemplary embodiments;

[0026] Figure 2 illustrates the labeling of the intermediate information bits s _u , where I e {0,1, "·,η} and i e {0,1, -· , Ν - 1} during polar encoding with N = 8, according to exemplary embodiments;

[0027] Figure 3 illustrates an exemplary encoder of a concatenation of polar code and an outer parity check code, according to some embodiments of the present disclosure;

[0028] Figure 4 illustrates an encoder with a cyclic redundancy check attachment, according to various embodiments;

[0029] Figure 5 illustrates a modified successive cancellation list (SCL) Polar decoder and deinterleaver, according to various embodiments;

[0030] Figure 6 illustrates an exemplary wireless network, according to various embodiments; [0031] Figure 7 illustrates example embodiments of a wireless device (or user equipment) in which embodiments of the present disclosure may be

implemented, according to various embodiments;

[0032] Figure 8 illustrates a virtualization environment in accordance with exemplary embodiments;

[0033] Figure 9 illustrates a flowchart showing a method of performing various functions described herein, according to various embodiments;

[0034] Figure 10 illustrates a flowchart showing a method of performing various functions described herein, according to various embodiments;

[0035] Figure 1 1 illustrates an exemplary virtualization apparatus in accordance with various embodiments; and

[0036] Figure 12 illustrates an exemplary virtualization apparatus in accordance with various embodiments. Detailed Description

[0037] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure. [0038] Radio Node: As used herein, a "radio node" is either a radio access node or a wireless device.

[0039] Radio Access Node: As used herein, a "radio access node" or "radio network node" is any node in a radio access network of a cellular

communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high- power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

[0040] Core Network Node: As used herein, a "core network node" is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P- GW), a Service Capability Exposure Function (SCEF), or the like.

[0041] Wireless Device: As used herein, a "wireless device" is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device. [0042] Network Node: As used herein, a "network node" is any node that is either part of the radio access network or the core network of a cellular communications network/system.

[0043] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0044] Note that, in the description herein, reference may be made to the term "cell;" however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0045] Particular embodiments include parity check (PC) bit generation for Polar codes. The embodiments may be classified into at least two groups of embodiments. A first group of embodiments includes cumulative summation, and a second group includes systematic coding of least reliable data bits.

[0046] In the first group of embodiments based on cumulative summation, in a particular embodiment each PC bit is equal to the sum of all previous bits in a non-recursive manner. That is, simple summation of all the information and frozen bits, excluding any previous PC bits, is used to generate the value of each particular PC bit.

[0047] Specifically, let u = [u ₀ , u _v ^■■■ , u _N _ ₁ ] represent the input vector of bits to the Polar encoder core, where N is the size of the Polar code, and let P denote the set of predetermined positions of PC bits. Then for each i e P, the value of the corresponding PC bit can be computed simply by

ui ⁼ ∑; ^' e{0,l,-,JV-l}\P:; ^' ≤i ^u j ^■

[0048] In other words, the value of each PC bit is the binary sum (i.e., XOR) of all bit values in front of it, except those values of other PC bits.

[0049] In another embodiment, each PC bit is equal to the sum of all previous bits in a recursive manner. That is, simple summation of all the information and frozen bits, including any previous PC bits, is used to generate the value of each particular PC bit. This can be achieved by shift register with feedback.

[0050] Specifically, let P = {i ₀ , i _v -· , Ϊ\Ρ\} sorted in such a way that i _m ≤ i _n whenever m≤n. Incrementing m sequentially from 0 to |P| (the number of elements in P), the value of the m-th PC bit can be computed simply by

Ui _m =∑je{0,l,-,N-l}:j≤i _m ^u j - [0051] In other words, the value of each PC bit is the binary sum (i.e. XOR) of all bit values in front of it, including those values of other previously computed PC bits.

[0052] In a second group of embodiments based on systematic coding of least reliable data bits, in a particular embodiment the PC bits are generated based on a systematic block code on the least reliable data bits. Specifically, let Λ c {0,1, -· , Ν - 1} denote the K _PC least reliable bit positions among the K bit positions that are chosen to carry data bits, where |Λ| = K _PC and K _PC < K. Also let Φ denote a K _PC by n _PC parity check matrix so that G = [I, Φ] forms the generator matrix of a (K _PC , K _PC + n _PC ) systematic code with a good minimum- distance property, where / denotes an K _PC by K _PC identity matrix. Let P =

[i ₀ , i _v ·· · , i _| p _| -i] be the position indices of the PC bits. Then for each i e P , the value of the m-th PC bit, where m = 0,1, ···, \P\ - 1, and without loss of generality, \P\ = n _PC is computed as

u _im = u _R ·

[0053] where denotes the m-th column of Φ, and u _R denotes a row vector formed by the elements in the set {u _j -. j e Λ} with indices sorted in ascending order. The vector u _R contains the data bits that are carried by the K _PC least reliable positions.

[0054] According to one aspect of this embodiment, the size of the set Λ (i.e., K _PC ) is selected based on the code rate R = (K + n _PC )/M, where M denotes the code length after rate-matching operations. In general, K _PC and n _PC are selected so that K _PC /(K _PC + n _PC ) is comparable to, or slightly below, the code rate R. That is, choosing (K _PC , n _PC ) such that

which provides a guideline for choosing K _PC for a given n _PC .

[0055] Figure 4 illustrates an encoder with a cyclic redundancy check attachment, according to various embodiments. Meanwhile, Figure 5 illustrates a modified successive cancellation list (SCL) Polar decoder and deinterleaver.

Embodiments disclosed herein could, for example, be implemented within environments utilizing such Polar encoding/decoding functionalities. [0056] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the

embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 6. For simplicity, the wireless network of Figure 6 only depicts network 106, network nodes 160 and 160b, and WDs 1 10, 1 10b, and 1 10c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (WD) 1 10 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

[0057] The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.1 1 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[0058] Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable

communication between devices.

[0059] Network node 160 and WD 1 10 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

[0060] As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi- standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E- SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network. [0061] In Figure 6, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of Figure 6 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0062] Similarly, network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC

component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple

NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access

technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

[0063] Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0064] Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality. For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

[0065] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband

processing circuitry 174 may be on the same chip or set of chips, boards, or units

[0066] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160, but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

[0067] Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

[0068] Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or WDs 1 10. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other

embodiments, the interface may comprise different components and/or different combinations of components.

[0069] In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0070] Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some

embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

[0071] Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[0072] Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective

components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

[0073] Alternative embodiments of network node 160 may include additional components beyond those shown in Figure 6 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

[0074] As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop- embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle- to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or

measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.

Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0075] As illustrated, wireless device 1 10 includes antenna 1 1 1 , interface 1 14, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 1 10 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1 10, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1 10.

[0076] Antenna 1 1 1 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1 14. In certain alternative embodiments, antenna 1 1 1 may be separate from WD 1 10 and be connectable to WD 1 10 through an interface or port. Antenna 1 1 1 , interface 1 14, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1 1 1 may be considered an interface.

[0077] As illustrated, interface 1 14 comprises radio front end circuitry 1 12 and antenna 1 1 1. Radio front end circuitry 1 12 comprise one or more filters 1 18 and amplifiers 1 16. Radio front end circuitry 1 14 is connected to antenna 1 1 1 and processing circuitry 120, and is configured to condition signals

communicated between antenna 1 1 1 and processing circuitry 120. Radio front end circuitry 1 12 may be coupled to or a part of antenna 1 1 1. In some

embodiments, WD 1 10 may not include separate radio front end circuitry 1 12; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 1 1 1. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 1 14. Radio front end circuitry 1 12 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1 12 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1 18 and/or amplifiers 1 16. The radio signal may then be transmitted via antenna 1 1 1. Similarly, when receiving data, antenna 1 1 1 may collect radio signals which are then converted into digital data by radio front end circuitry 1 12. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0078] Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 1 10 components, such as device readable medium 130, WD 1 10 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein. [0079] As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of WD 1 10 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 1 14. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

[0080] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 1 10, but are enjoyed by WD 1 10 as a whole, and/or by end users and the wireless network generally.

[0081] Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1 10, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0082] Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be considered to be integrated.

[0083] User interface equipment 132 may provide components that allow for a human user to interact with WD 1 10. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 1 10. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 1 10. For example, if WD 1 10 is a smart phone, the interaction may be via a touch screen; if WD 1 10 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 1 10, and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 1 10, and to allow processing circuitry 120 to output information from WD 1 10. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 1 10 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[0084] Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary

depending on the embodiment and/or scenario.

[0085] Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 1 10 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 1 10 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1 10 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 1 10 to which power is supplied.

[0086] Figure 7 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 2200 may be any UE identified by the 3 ^rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in Figure 7, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 ^rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 7 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa. [0087] In Figure 7, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 21 1 , memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231 , power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 7, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0088] In Figure 7, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0089] In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0090] In Figure 7, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 21 1 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 21 1 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 21 1 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

[0091] RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read- only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

[0092] Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any

combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221 , which may comprise a device readable medium. [0093] In Figure 7, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE,

UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit

components, software or firmware, or alternatively may be implemented separately.

[0094] In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

[0095] The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware. [0096] Figure 8 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0097] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

[0098] The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

[0099] Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

[0100] Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

[0101] During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

[0102] As shown in Figure 8, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

[0103] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0104] In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

[0105] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in Figure 8.

[0106] In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0107] In some embodiments, some signaling can be effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

[0108] Figure 9 depicts a method in accordance with particular

embodiments, the method begins at step 900 with a wireless transmitter (e.g., wireless device 1 10, network node 160, etc.) that receives a set of information bits. For example, network node 160 may receive a set of information bits from a higher layer for transmission to wireless device 1 10. [0109] At step 910, the wireless transmitter determines a set of parity check bits. For example, network node 160 may determine a set of parity check bits by, for each parity check bit in the set, determining the binary sum of all bit values in front of it. Some embodiments may include other parity bits in the sum, while others may not include the parity bit. In other embodiments, network node 160 may generate a set of parity check bits based on a systematic block code on the least reliable bits of the set of information bits and frozen bits. In particular embodiments, the wireless transmitter may determine the set of parity check bits according to any of the embodiments and examples described above.

[0110] At step 920, the wireless transmitter concatenates the set of information bits with the set of parity check bits. For example, network node 160 may combine the set of parity check bits with the set of information bits according to any of the embodiments and examples described above.

[0111] At step 930, the wireless transmitter Polar encodes the information bits into a set of information bits and frozen bits. For example, network node 160 may encode the information bits according to the Polar encoding algorithm described above.

[0112] At step 940, the wireless transmitter transmits the encoded set of bits to a wireless receiver. For example, network node 160 may transmit the concatenated bits to wireless device 1 10.

[0113] Modifications, additions, or omissions may be made to the method illustrated in Figure 9. Additionally, one or more steps in method the method of Figure 9 may be performed in parallel or in any suitable order. [0114] Figure 10 depicts a method in accordance with particular embodiments, the method begins at step 1000 with a wireless receiver (e.g., wireless device 1 10, network node 160, etc.) that receives a set of polar coded information bits concatenated with a set of parity check bits. For example, wireless device 1 10 may receive a set of polar coded information bits

concatenated with a set of parity check bits from network node 160 (e.g., as described with respect to Figure 9).

[0115] At step 1010, the wireless receiver polar decodes the set of polar coded information bits concatenated with the set of parity check bits. For example, wireless device 1 10 may decode the information bits according to the Polar encoding algorithm described above.

[0116] At step 1020, the wireless receiver terminates the decoding when one of the parity check bits in the set of parity check bits indicates an error. For example, wireless device 1 10 may terminate the decoding early once an error is detected, according to any of the embodiments and examples described above.

[0117] Modifications, additions, or omissions may be made to the method illustrated in Figure 10. Additionally, one or more steps in method the method of Figure 10 may be performed in parallel or in any suitable order.

[0118] Figure 1 1 illustrates a schematic block diagram of an apparatus 1 100 in a wireless network (for example, the wireless network shown in Figure 6). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 1 10 or network node 160 shown in Figure 6). Apparatus 1 100 is operable to carry out the example method described with reference to Figure 9 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 9 is not necessarily carried out solely by apparatus 1 100. At least some operations of the method can be performed by one or more other entities.

[0119] Virtual Apparatus 1 100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special- purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as

instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 1110, encoding unit 1120, transmitting unit 1130, and any other suitable units of apparatus 1 100 to perform corresponding functions according one or more embodiments of the present disclosure.

[0120] As illustrated in Figure 1 1 , apparatus 1 100 includes receiving unit 1 1 10, encoding unit 1 120, and transmitting unit 1 130. Receiving unit 1 1 10 is configured to receive a set of information bits for encoding and transmission. Encoding unit 1 120 is configured to; determine a set of parity check bits; and concatenate the set of information bits with the set of parity check bits; and Polar encode the information bits into a set of information bits and frozen bits.

Transmitting unit 1 130 is configured to transmit the encoded bits to a wireless receiver.

[0121] Figure 12 illustrates a schematic block diagram of an apparatus 1200 in a wireless network (for example, the wireless network shown in Figure 6). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 1 10 or network node 160 shown in Figure 6). Apparatus 1200 is operable to carry out the example method described with reference to Figure 10 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 10 is not necessarily carried out solely by apparatus 1200. At least some operations of the method can be performed by one or more other entities.

[0122] Virtual Apparatus 1200 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special- purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as

instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 1210 and decoding unit 1220, and any other suitable units of apparatus 1200 to perform corresponding functions according one or more embodiments of the present disclosure.

[0123] As illustrated in Figure 12, apparatus 1200 includes receiving unit 1210 and decoding unit 1220. Receiving unit 1210 is configured to receive encoded bits, such as the information encoded according to Figure 9. Decoding unit 1220 is configured to Polar decode the received bits using the parity bits described in the embodiments and examples described above.

[0124] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description. [0125] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Reference List

[1 ] E. Arikan, "Channel Polarization: A Method for Constructing Capacity- Achieving Codes for Symmetric Binary-Input Memoryless Channels," IEEE Transactions on Information Theory, vol. 55, pp. 3051 -3073, Jul. 2009.

[2] I. Tal and A. Vardy, "List Decoding of polar codes," in Proceedings of IEEE Symp. Inf. Theory, pp. 1 -5, 201 1.

[3] Leroux, et. al., "A Semi-Parallel Successive-Cancellation Decoder for Polar Codes," IEEE TRANSACTIONS ON SIGNAL PROCESSING, VOL. 61 , NO. 2, JANUARY 15, 2013.

Abbreviations

[0126] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

1x RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DCI Downlink Control Information

DFTS OFDM Discrete Fourier Transform Spread OFDM

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI

eNB E-UTRAN NodeB

ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

FFS For Further Study GERAN GSM EDGE Radio Access Network

gNB Base station in NR

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

IR-HARQ Incremental Redundancy HARQ

LLR Log Likelihood Ratio

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference SC Successive Cancellation

SCL Successive Cancellation List

SCH Synchronization Channel

SCell Secondary Cell SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network

SS Synchronization Signal

SSB Synchronization Signal Block

SSS Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network