Page 825 - 5G Basics - Core Network Aspects
P. 825

Transport aspects                                              2


                                    Table 11-9 – OLR commands sent by the initiating FTU

                  Name        Length (bytes)   Byte                    Content                    Support
                                                        A variable number of bytes describing
                                                        subcarrier parameter field for each
                                                        subcarrier.
                                                 2      0416  (Note 1)
                                                 3      Segment code (SC)
                                                 4      [0000 aaaa]
                                                        aaaa = RPA configuration change count
             OLR request type

             4 (update RMC
                              8+2 × NSCR                                                        Mandatory
             parameters)                      5 and 6   Two bytes for the number of subcarriers of
             (RPA)                                      the updated RTS (NSCR).
                                              7 and 8   CNTSF at which new settings to be applied.
                                             9 to 9 + 2 ×  2  NSCR bytes describing the subcarrier
                                              NSCR − 1   parameter field for each subcarrier.
                                                 2      0516 (Note 1)


                                              3 and 4   Downstream RMC transmission schedule
                                                        represented as a bit map:
                                                        0 – indicates an inactive TDD frame
                                                        1 – indicates an active TDD frame
                                                        The LSB of byte 4 corresponds to the TDD
                                                        sync frame (index 0). The MSB of byte 4
                                                        corresponds to the TDD frame with index 7.
                                                        The LSB of byte 3 corresponds to the TDD
             OLR request type                           frame with index 8 (see clause 10.6). Bits
             5                                          corresponding with an index ≥ MSF shall be set
             (L2TSA: L2       7                         to 0.                                   Mandatory
             transmission                     5 and 6   Upstream RMC transmission schedule
             schedule                                   represented as a bit map:
             adaptation)                                0 – indicates an inactive TDD frame
                                                        1 – indicates an active TDD frame
                                                        The LSB of byte 6 corresponds to the TDD
                                                        sync frame (index 0). The MSB of byte 6
                                                        corresponds to the TDD frame with index 7.
                                                        The LSB of byte 5 corresponds to the TDD
                                                        frame with index 8 (see clause 10.6). Bits
                                                        corresponding with an index ≥ MSF shall be set
                                                        to 0.
                                                 7      [0000 aaaa]
                                                        aaaa = L2 configuration change count (L2CCC)
             NOTE 1 – All other values for this byte are reserved by ITU-T.
             NOTE 2 – Setting bb=00 is only valid for a TIGARESP (see clause 13.2.2.1).
             NOTE 3 – Setting N f = 0 is valid and shall be used if the OLR command of OLR request type 2 is confirming the settings requested
             by TIGA.
             NOTE 4 – If used in the upstream direction, OLR request type 1 can only be used as an autonomous SRA or bit swapping and
             d_SRA shall be set to 1. It is implied that all gains g i will remain unchanged.
             NOTE 5 – If used in downstream, all gains shall be set to 1. It is implied that d_SRA =1.
             NOTE 6 –The b i values indicated in the NOI subcarrier parameter block shall not be applied to RMC subcarriers.











                                                                                                         815
   820   821   822   823   824   825   826   827   828   829   830