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

2                                                 Transport aspects




                               Table 11-48.6 – L2 link state transition response (FTU-R to FTU-O)

                                      Length
                     Name                                Byte                         Content
                                      (Bytes)
             L2.1-Exit-Confirm           2                2            8616 (Note 1)

             L2.2-Exit-Confirm           2                2            8516 (Note 1)
             L2.1-Transition-Confirm     2                2            8716 (Note 1)
             NOTE 1 – All other values are reserved by ITU-T.
             NOTE 2 – The value of the SCCC shall be advanced relative to the last downstream SCCC value prior to any link state transition,
             independent of the particular link state transition.
             NOTE 3 – The formatting of the subcarrier field and the valid range of the values shall be the same as those specified for OLR
             type 1 (see clause 11.2.2.5 and Tables 11-10 and 11-11). The field shall be encoded with increasing subcarrier index.
             NOTE 4 – For good practice, the value of R FEC should not be less than 8.


                              Table 11-48.7 – Battery powered status response (FTU-O to FTU-R)


                   Name          Length (Bytes)         Byte                         Content
             Acknowledge              2                  2                         8416 (Note 1)
             battery powered
             status
             NOTE – All other values are reserved by ITU-T.

            11.2.2.17  DRR configuration commands and responses

            The FTU-O shall use the DRR configuration commands to send the value of NDRR and NRM to the FTU-R and
            to send the DRR configuration request data to the FTU-R (see clause 8.1.1). The command shall be sent by
            the FTU-O only. The FTU-R shall respond to the DRR request command using DRR.confirm and shall respond
            to the DRR configuration request command using DRR.config.confirm, respectively.

            The first byte of the commands and responses shall be the assigned  value DRR configuration command
            type, as shown in Table 11-5 (normal priority command). The second and subsequent bytes shall be as
            defined in Table 11-49 (for the commands) and in Table 11-50 (for the responses). The bytes shall be sent
            using the format described in clause 11.2.2.1.


                               Table 11-49 – DRR configuration commands (sent by the FTU-O)

                 Name        Length (bytes)   Byte                           Content
             DRR request           4           2     0116 (Note 1)

                                               3     One byte for NDRR represented as an unsigned integer.
                                               4     One byte for NRM (see Table 8-3) represented as an unsigned
                                                     integer.
             DRR                Variable       2     0216 (Note 1)
             configuration                     3+    DRR data as received from the DRA function at the FTU-O (see
             request
                                                     Table 8-3). The format of the DRR data is defined in Table Y-2.
             NOTE 1 – All other values for byte 2 are reserved by ITU-T.












            842
   847   848   849   850   851   852   853   854   855   856   857