tech-invite   World Map
3GPP     Specs     Glossaries     UICC       T+       IETF     RFCs     Groups     SIP     ABNFs       Search     Home
Top        in Index        Prev        Next

TS 32.154 (SA5)
Telecommunication management –
Backward and Forward Compatibility (BFC); Concept and definitions

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    16 p.
(P) V13.0.0    2016/01    16 p.
(P) V12.0.0    2014/10    16 p.
(P) V11.0.0    2012/09    16 p.
(P) V10.0.0    2010/04    16 p.
(P) V9.0.0    2009/12    16 p.
(P) V8.0.0    2008/12    16 p.
(P) V7.0.0    2007/06    16 p.


Rapporteur:  Mr. Petersen, Robert
See also:  –


This TS gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.

The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.

Clause 4 specifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable.


 

Here        Top