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

Transport aspects                                              2


            The FTU-O may reject a L3 Request using reason code 0116 if it is temporarily busy, or reject it using code
            0316 if it has local knowledge that the L3 state is not desired at this time. Upon receipt of a L3 Request, the
            FTU-O may reply with a Grant and immediately start transition into the L3 state.
            If the FTU-R receives the Grant response, the FTU-R shall stop transmitting. When the FTU-O observes the
            stopped transmission, it shall transition into O-DEACTIVATING1 state (see clause 12.1.2).

            11.2.2.12.2 L3 Request by FTU-O
            Upon receipt of a L3 Request, the responding FTU-R shall send either a Grant or a Reject response. If the
            format of the command is different than one presented in Table 11-34, the Reject response shall be sent
            with the reason code 0216.

            The FTU-R may reject a L3 Request using reason code 0116 if it is temporarily busy, or reject it using code
            0316 if it has local knowledge that the L3 state is not desired at this time. Upon receipt of a L3 Request, the
            FTU-R may reply with a Grant and immediately start transition into the L3 state.

            If  the  FTU-O  receives  the  Grant  response,  the  FTU-O  shall  transition  into  O-DEACTIVATING1  state  (see
            clause 12.1.2). When the FTU-R observes that the FTU-O transitioned to the O-DEACTIVATING1 state, it
            shall stop transmitting.

            11.2.2.13  PMD test parameter read commands and responses
            The PMD test parameter read commands shall be used to retrieve the values of the PMD test parameters
            that  are  specified  in  clause  11.4.1  and  maintained  by  the  far-end  FTU.  The  PMD  test  parameter  read
            commands are shown in Table 11-37, and may be initiated by either FTU. The responses shall be as shown
            in  Table  11-38.  The  first  byte  of  all  PMD  test  parameter  read  commands  and  responses  shall  be  the
            assigned value for the PMD test parameter read command type, as shown in Table 11-5. The subsequent
            bytes of the commands shall be as shown in Table 11-37. The subsequent bytes of the responses shall be as
            shown in Table 11-38. The bytes shall be sent using the format described in clause 11.2.2.1.


                         Table 11-37 – PMD test parameter read commands sent by the requesting FTU

                            Length
                 Name                  Byte                        Content                         Support
                            (bytes)
             Single read      2         2      0116 (Note 1)                                    Mandatory
             Vector block     7         2      0616 (Note 1)                                    Mandatory
             read
                                               One byte containing the ID of the vector test parameter
                                               to be read (Note 2).
                                        3
                                               0416: SNR per subcarrier group (Note 3).
                                               0516: Downstream ALN per subcarrier group.
                                      4 and 5   Two bytes describing the start subcarrier group index.
                                      6 and 7   Two bytes describing the stop subcarrier group index.
             NOTE 1 – All other values for byte 2 are reserved by the ITU-T.
             NOTE 2 – All other values for byte 3 are reserved by the ITU-T.
             NOTE 3 – The only valid value of subcarrier group size (G) for SNR is G = 1.


















                                                                                                         829
   834   835   836   837   838   839   840   841   842   843   844