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

2                                                 Transport aspects


                                                        Annex S


                                                NT software upgrade
                                  (This annex forms an integral part of this Recommendation.)


            Editorial note: This annex was introduced by Cor.3 to ITU-T G.9701, but is not shown in revision marks for
            readability purposes.

            S.1     Scope

            This  annex  provides  means  to  upgrade  the  software  of  an  NT  where  the  executable  software  can  be
            upgraded with a single vendor-specific image file. The executable software may exist in multiple parts of
            the equipment (e.g., DSP firmware and higher layer application software). Two images are maintained at
            the NT so that one can be upgraded while the other one is executed. The contents of this software image
            file and the upgrade of individual components of an NT are beyond the scope of this annex.

            This annex is beyond the scope of transceiver functionality and is optional for system implementations.

            S.2     References
            [IETF RFC 1321]     R. Rivest, "The MD5 Message-Digest Algorithm, 1992", IETF RFC 1321, April 1992.

            [ITU-T I.363.5]      Recommendation ITU-T I.363.5 (1996), B-ISDN ATM Adaptation Layer specification :
                                Type 5 AAL.

            S.3     Reference model
            The reference model for the NT software upgrade is shown in Figure S.1. It contains the associated OAM
            entities of the DPU and NT. The DPU entity contains the software image management function as a part of
            the ME-O. The ME-O will act as a master for the software image upgrades at the ME-R, which contains two
            instances of software images (0 and 1). Those two instances of software images at the NT are managed
            independently by the software management function of the DPU. Additional vendor specific files may be
            managed (see clause S.4.2).






















                                  Figure S.1 – Software image management reference model


            The  status  of  each  software  image  at  the  ME-R  is  reflected  in  DPU-MIB.  The  ME-O  and  ME-R  use  a
            transparent  communication  channel  to  exchange  software  management  commands  and  data  between
            them as system-related OAM data. The clauses of this annex describe the software image management
            process and the details of messages exchanged.





            998
   1003   1004   1005   1006   1007   1008   1009   1010   1011   1012   1013